DDoS depends on public addresses acting as a clients pounding your DNS server with thousands of recursive queries at once. If your DNS server isn't public, then it isn't a open resolver, and a client on the internet can't query it directly.

In our case, we have a local DNS server, available to the internet, as a backup to our ISP-hosted DNS. This server is typically vulnerable. But it's set with a higher cost so it won't be used unless ISP goes down.

Sweet. Thanks for getting this for us @adam-ierymenko

@scottalanmiller said in Renaming a Windows Computer from the Command Line:

@IRJ said in Renaming a Windows Computer from the Command Line:

@scottalanmiller said in Renaming a Windows Computer from the Command Line:

@IRJ said in Renaming a Windows Computer from the Command Line:

I learned something new today. I have been using the shutdown command for years. I never realized you could rename a PC with it.

shutdown doesn't do the renaming, you just have to reboot after you rename.

I use "m" instead of c for computer name

/c is the comment for the logs to tell them that you just "Renamed Machine", it doesn't rename it, it literally puts "Renamed Machine" into the reboot logs.

Ok. Got ya.

@dafyre said in Installing Scale Tools on Windows Server Core from Command Line:

@scottalanmiller said in Installing Scale Tools on Windows Server Core from Command Line:

@dafyre said in Installing Scale Tools on Windows Server Core from Command Line:

@scottalanmiller said in Installing Scale Tools on Windows Server Core from Command Line:

@dafyre said in Installing Scale Tools on Windows Server Core from Command Line:

I'm unfamiliar with the Server Core setup... but can't you install these drivers as part of the Windows installation process?

Storage yes, but I'm unaware of a simple way during a stock install to include other drivers. The storage ones are requested, and necessary, during the install. Otherwise the installation location does not show up (unless you don't use VirtIO block devices.) You can definitely add the tools into an image, and there is probably a way to include Ethernet devices ahead of time, but I'm not used to the installation process to know where it happens.

I just select all 3 of the INF files and go... It's always installed everything for me, lol... Just point it at the folder for the right OS and 32 or 64 bit... (Note: This is the way I did it in Scale v4.3... I've not had a chance to use their newer stuff yet.

At what stage are you selecting them?

During the install process... the same place where you go when you're picking the storage drivers.

I rarely do modifications at that stage. Still, handy to have a simple option because a lot of people will get the install done and find that there is no networking and need to know what to do at that point. 🙂

@thwr said in Simple guide to diagnosing Account Lockouts:

Locked AD accounts due to bad passwords
https://mangolassi.it/topic/9709/monitoring-ad-users/12

Thanks. I added the link to the comment section on the article.

@Dashrender said in Tracking the origination of a shadow copy:

I suppose you could easy enough with an agent, thinking backups here.

Precisely. As the origination is the same machine and not the backup device, I guess that answers that.

@aaronstuder said in Moving to a New WSUS server:

@BBigford No Problem. Once I realized that the port numbers change, I realized the issue right away.

Clients are being seen by the WSUS server now 🙂

Sweet!

Looks great !!

Thanks for the doc.

Downloading? It was done downloading before my finger was off the mouse, lol.

I can't wait to dive into 2016, though. They're bringing a lot of improvements that me and this team I am with here are excited about in the RemoteApp and VDI realms.

https://blogs.msdn.microsoft.com/microsoft_press/2016/04/20/free-ebook-introducing-windows-server-2016-technical-preview/

No, it doesn't support this. RAID 1, you are correct, but Parity RAID 5 or 6 it does not. The OS needs to be up and running to be able to manage the parity RAID so you can't use it for the system install, only for extra data volumes.

@scottalanmiller said:

@Dashrender said:

@tonyshowoff said:

@scottalanmiller said:

That's why NO ONE complains about the minimum wage being too high, they complain that the minimum wage is "too close to their wage."

Definitely seen that a lot, it's weird.

I've completely missed this on Facebook somehow.

Oh it is huge. I've seen it from a lot of different people... mostly those that earn only a little more than $15/hr and/or military. I've also seen military people mocking those people for not understanding how pay works in the private world.

I've seen the low wage workers arguing this. I have also seen high wage and business owners making the same argument. Everyone I know in the military, except for that one RWNJ who joined just to shoot people, is for a wage increase.

That's the big thing with XenApp, application performance. And integration with XenDesktop for VDI.

@JaredBusch said:

@BRRABill said:

@scottalanmiller said:

Apparently, when have they NOT? Where does this "first release" myth come from? Other than the unique case of Vista, which was a true first release of NT 6. This is NOT a first release, this is the latest version of NT 6. If you have concern about lower releases, then that would make you install this as this is the latest update to NT 6.

On the desktop side, I typically have always felt the first releases (like the now defunct Windows 😎 to be shaky. I do not think that is a myth.

There was not a single functionality issue with Windows 8.
Honestly, there was not a single problem with Vista either as long as your hardware worked with it. Vista had a driver compatibility problem.

Well this is not entirely true. Vista also included a brand new network stack that they wrote that had TONS of holes in it. They dumped that stack with 8.1 though.

Here is an example:

Three hosts, each running two Windows Server VMs, each with two sockets. Say Dell Power Edge R610 or HP Proliant DL360 nodes. Windows Standard Licensing.

Cost per license: ~$700

To license each node to run its normal load is $700 for a total of $2,100.

If we want to address the ability of any node to be a failover for the others or for non-disruptive maintenance, we need an additional license per machine. So we suddenly jump from $700 per node to $1,400 per node and the whole cluster jumps to $4,200 while gaining nothing during normal production times.

Now that only addresses single node failover. If we want to maintain the ability to do failover during times of maintenance we need yet another license for each machine! That means $2,100 per machine and $6,300 for the cluster.

Suddenly $350 per virtual machine in licensing has exploded to $1,050. A non-trivial increase.

Now we can choose which level and which features we want, but typically the value of an inverted pyramid is sold based on this top level of flexibility. If we are dealing with Data Center licensing this is more obvious and far less complex, but SMBs would rarely pay for that level of workload and may not think through the additional costs that this style of architecture potentially bring to the table.

What was wrong?

Good way to think of it. Clean install is a little extra work today in exchange for a "known" or nearly known environment. An in place upgrade means carrying risk with you, maybe a little, but some that might bite you later.

Or maybe the next IT guy, just leave the headaches for him 😉

I love Red Gate. Their stuff is certainly not free, but ever piece of their software I have purchased has been well worth the cost.

@scottalanmiller said:

@Dashrender you have to have Dynamic Disks to do this in Windows using MS tools.

Sure, but you don't when using third party tools. Again, I haven't done it in 4+ years, so I don't know what Acronis can currently do.

@lance said:

I thought I read some where that Microsoft is making the jump from 6.4 to 10, which will be the first time the os and kernel match. I could be wrong though.

Linux did a renumbering too, recently, to make the number more marketable. But 3.0 is actually part of the 2.6 family. At best you could consider it 2.8. Microsoft may do the same thing, switch from a meaningful numbering to a marketing number. But the new kernel is remaining part of the Vista kernel family.